Integrating policies from a plurality of disparate management agents

ABSTRACT

Described herein are embodiments for managing policies of a mobile device. In embodiments, a mobile device receives policy containers from a plurality of disparate management agents. Each policy container has one or more policies. Each policy corresponds to a particular category that governs various aspects of the device. The policies described herein may be device wide policies corresponding to various features on the device. The policies may also be data specific policies which dictate how data is stored on and transferred to and from the device. Once the policies are received, a determination is made as to which policy in each category is the most secure policy. The most secure policy for each category is merged to create a global policy that is applied to the mobile device.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation application of U.S. patentapplication Ser. No. 14/546,262 (now U.S. Pat. No. 9,800,616), entitled“INTEGRATING POLICIES FROM A PLURALITY OF DISPARATE MANAGEMENT AGENTS,”filed on Nov. 18, 2014, which application is a continuation applicationof U.S. patent application Ser. No. 12/334,232 (now U.S. Pat. No.8,931,033), filed on Dec. 12, 2008, the entire disclosures of which arehereby incorporated herein by reference.

BACKGROUND

Protecting digital networks and the data contained therein is typicallygoverned by numerous digital policies that are pushed to computingdevices on the networks. These policies have been extended to mobilecomputing devices. Each mobile device is managed by a single managementagent and users are restricted from utilizing their mobile device inenvironments managed by other disparate management agents. Users mayalso be restricted from downloading content provided by the disparatemanagement agents. Current solutions require that an IT administratorestablish a number of trusted links among each of the disparatemanagement agents. However, this solution does not scale beyond a smallnumber of management agents and is not user initiated.

It is with respect to these and other considerations that embodiments ofthe present invention have been made. Also, although relatively specificproblems have been discussed, it should be understood that embodimentsof the present invention should not be limited to solving the specificproblems identified in the background.

SUMMARY

This summary is provided to introduce a selection of concepts in asimplified form that are further described below in the DetailDescription section. This summary is not intended to identify keyfeatures or essential features of the claimed subject matter, nor is itintended to be used as an aid in determining the scope of the claimedsubject matter.

Described herein are embodiments for managing policies of a mobiledevice. In embodiments, a mobile device receives policy containers froma plurality of disparate management agents. Each policy container hasone or more policies. Each policy corresponds to a particular categorythat governs various aspects of the device. The policies describedherein may be device wide policies corresponding to various features onthe device. The policies may also be data specific policies whichdictate how data is stored on and transferred to and from the device.Once the policies are received, a determination is made as to whichpolicy in each category is the most secure policy. The most securepolicy for each category is merged to create a global policy that isapplied to the mobile device.

Embodiments may be implemented as a computer process, a computing systemor as an article of manufacture such as a computer program product orcomputer readable media. The computer program product may be a computerstorage media readable by a computer system and encoding a computerprogram of instructions for executing a computer process. The computerprogram product may also be a propagated signal on a carrier readable bya computing system and encoding a computer program of instructions forexecuting a computer process.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments of the present disclosure may be more readily described byreference to the accompanying drawings in which like numbers refer tolike items and in which:

FIG. 1 illustrates an embodiment of a mobile device receiving policiesand data from a plurality of disparate management agents.

FIG. 2 is an operational flow for managing policies of a mobile device.

FIG. 3 is an operational flow for performing updates to the managementpolicies of the mobile device.

FIG. 4A illustrates the merging policies from a plurality of disparatemanagement agents.

FIG. 4B illustrates merging updated policies from a plurality ofdisparate management agents.

FIG. 4C illustrates merging updated policies from a plurality ofdisparate management agents when a relationship between the managementagent and the mobile device has been severed.

FIG. 5 illustrates a merging rule for merging policies from a pluralityof disparate management agents.

FIG. 6 illustrates a second merging rule for merging policies from aplurality of disparate management agents.

FIG. 7 illustrates a computing environment for implementing embodiments.

DETAILED DESCRIPTION

Various embodiments are described more fully below with reference to theaccompanying drawings, which form a part hereof, and which show specificembodiments for practicing the invention. However, embodiments may beimplemented in many different forms and should not be construed aslimited to the embodiments set forth herein; rather, these embodimentsare provided so that this disclosure will be thorough and complete, andwill fully convey the scope of the invention to those skilled in theart. Embodiments may be practiced as methods, systems or devices.Accordingly, embodiments may take the form of a hardware implementation,an entirely software implementation or an implementation combiningsoftware and hardware aspects.

FIG. 1 illustrates a distributed system with a plurality of managementagents (management agent [1] 110, management agent [2] 120, andmanagement agent [n] 130) connected to a mobile device 150 through anetwork. In embodiments, the management agents are exchange servers.Each exchange server may have one or more corresponding policies. Inother embodiments, the management agents may be system managementservers, third party servers, or any combination thereof.

Although only three management agents are shown, it is contemplated thatthe mobile device 150 may connect to any number of management agents. Inembodiments, the mobile device 150 may be a smart phone, cell phone,personal digital assistant (PDA), or other handheld device capable ofconnecting to a network. Each of the plurality of management agentsprovides policies 115, 125, 135 and data 116, 126, 136 to the mobiledevice 150. These policies govern the properties of the mobile device150 including the functionality of various components of the device(e.g., camera, smart card reader, etc.). The policies also govern howdata is stored on and transferred to and from the device.

Mobile device 150 may also receive data from one or more unmanagedentities 140. In contrast to the management agents, the unmanagedentities do not require that the mobile device 150 adheres to any of thevarious policies. According to embodiments, the mobile device 150 isconnected to both an unmanaged entity and management agent. If however,any one of the unmanaged entities are associated with one of themanagement agents that issued a policy that policy may still be appliedon data received from the unmanaged entity.

Prior to receiving the data from any one of the management agents 110,120, 130, the mobile device 150 may establish a relationship with, anddownload one or more policies from each management agent. Alternatively,the mobile device 150 may already have an established relationship withone management agent, such as management agent 110. Management agent 110may update or change its policy. In response to the update, mobiledevice 150 may download the updated policy from the management agent 110and the new policy may be applied to the mobile device 150.

In embodiments, once the policies of the management agent or server havebeen downloaded, the mobile device 150 receives a temporary policy key.The policy key indicates to the plurality of management agents that thepolicies issued by each management agent will be enforced on the mobiledevice 150.

According to embodiments, each management agent transmits a policycontainer having one or more policies to the mobile device 150. Inembodiments the policy container is a set of policies issued by amanagement agent. Each policy in the policy set governs specific aspectsof the device. Each policy corresponds to a specific category thatrelates to various features and aspects of the mobile device 150. Forexample, the categories may include: a Personal Identification Number(PIN) lock category having policies that require the mobile device toautomatically lock itself after a specific amount of inactivity; a PINlength category having policies that require that a password for thedevice has a certain number of characters; a Bluetooth enablementcategory having policies that either enable or disable the Bluetoothcapabilities of the mobile device 150; and a maximum number of emailscategory having policies that set a maximum number of email messagesthat may be stored on the mobile device 150. Although specificcategories have been mentioned, it is contemplated that many morecategories relating to the controls and management of the device may beincluded.

For example, the mobile device 150 may receive a policy container havingtwo policies from management agent [1] 110, a second policy containerhaving three policies from management agent [2] 120, and a third policycontainer having two policies from management agent [n] 130. Each policyin each of the policy containers received from the management agent maybe associated with a separate category. Alternatively, a managementagent may issue at least one policy that belongs in the same category asa policy issued by at least one other management agent. For example,management agent [1] 110 may issue a policy container that includes aPIN Lock policy and a password length policy. Management agent [2] 120may issue a policy container having a PIN lock policy, a password lengthpolicy, and a policy that prohibits email attachments from beingreceived on the mobile device 150. Yet another management agent,management agent [n] 130 may issue a policy container that contains anemail encryption policy, requiring all email messages sent to and fromthe mobile device 150 to be encrypted, and a disable Bluetooth policy.

As previously discussed, each of the policies, including those listedabove, may be either device wide policies or data specific policies. Thedevice wide policies are policies that may be merged with all otherdevice wide policies issued from each of the management agents. The dataspecific policies are policies which may, in some embodiments, be mergedwith other data specific policies and/or may be merged with the devicewide policies. The data specific policies govern each account (e.g.,various email accounts associated with each management agent orunmanaged entity) associated with the device. Data specific policiesalso govern how data is transferred to and from the device and how thedata is stored on the device. For example, a data specific policy mayrequire that only encrypted data may be sent to and from the mobiledevice 150. A data specific policy may also require that HTML mail beeither enabled or disabled on the mobile device 150. The data specificpolicies may also correspond to secure Multipurpose Internet MailExtension (SMIME) settings as well and truncation and filtering of data.

Once all policy containers from each of the plurality management agentsare received, or when a new policy container from a new management agenthas been received, the policies in each category are compared with theother policies in the same category to determine which policy is themost secure. When the most secure policy of each category has beendetermined, each of the most secure policies are merged to create aglobal policy. Therefore, the resulting global policy is at least assecure as any of the individual policies from each management agent. Inembodiments, it does not matter which management agent issued each ofthe most secure policies in each category or whether each managementagent is the same type of server (e.g. exchange server). Once the globalpolicy has been created, the global policy is applied to the mobiledevice 150 when the mobile device 150 connects to each of the variousmanagement agents.

FIGS. 2-3 illustrate operational flows 200 and 300 for managing policiesof a mobile device according to embodiments. Operational flows 200 and300 may be performed in any suitable computing environment. For example,the operational flows may be executed by systems such as the systemdescribed in FIG. 1. Therefore, the description of operational flows 200and 300 may refer to at least one of the components of FIG. 1. However,any such reference to components of FIG. 1 are for descriptive purposesonly.

Operational flow 200 begins at Step 210 in which policy containers arereceived by the mobile device 150 (FIG. 1). The policy containers maycontain one or more policies. Each of the one or more policies maygovern a specific aspect of the device or govern data management aspectsof the device. In an embodiment, each policy corresponds to one of aplurality of categories. Such examples include a PIN lock category, apassword length category, etc.

Once the policy containers have been received by the mobile device, step220 provides that each policy in each category is compared with allother policies in the same category, to find the most secure policy ineach category (e.g. a password length category). In embodiments, thiscomparison is performed on each policy of each category regardless ofwhich management agent provided the policy. For example, if managementagent [1] 110 has a policy requiring that the mobile device 150 have apassword with a minimum character length of four, and management agent[2] 120 has a policy requiring the mobile device 150 to have a passwordwith a minimum length of five, these two policies are compared todetermine which policy is the most secure. Because a password havingfive characters is more secure than a password having four characters,the policy requiring the password of five characters will be the policythat is enforced on the mobile device 150.

It is also contemplated that a management agent may issue a policy typethat the other management agents in the system did not issue. Forexample, management agent [n] 130 may have issued a policy that requiresthe mobile device 150 to disable Bluetooth capabilities. In embodiments,it may be determined that disabling Bluetooth capabilities of the mobiledevice 150 is more secure than allowing the Bluetooth capabilities to beenabled. Thus, the Bluetooth policy will be determined to be the mostsecure in the Bluetooth policy category and the policy will be appliedto the mobile device 150. Even though management agent [n] 130 is theonly management agent requiring that this policy be enforced, thispolicy will be globally enforced because it is determined to be the mostsecure.

Once the most secure policy from each category has been determined, step230 provides that the policies are merged together to create anaggregate list or global policy. In embodiments, the global policy maycontain one or more policies from each of the plurality of managementagents. Alternatively, one management agent may have issued the mostsecure policy for each category. In such instances, the policies issuedby this particular management agent will be enforced when the mobiledevice connects to each of the other management agents.

According to embodiments, there are a number of different merging rulesthat may be applied when creating the global policy. Each of these rulesmay be applied when device wide policies are merged, when data specificpolicies are merged, or when a combination of device wide and dataspecific policies are merged. A few examples of merging rules aredescribed below. However, it should be appreciated that the presentdisclosure is not limited to the specific rules described below andother embodiments may include different merging rules not describedbelow. In some embodiments, a number of, or combination of, individualmerging rules may be applied.

One merging rule is a binary merging rule. According to the binarymerging rule, an enablement bit is set which overrides any off bit of apolicy or, the inexistence of a policy. For example, if management agent[1] 110 requires that the mobile device 150 be PIN locked after aspecified time of inactivity and second management agent [2] 120 did notissue a similar policy, the policy from management agent [1] 110 isdetermined to be the most secure policy in that particular category(e.g. the PIN lock category). Thus, regardless of whether the mobiledevice 150 connects to management agent [1] 110 or management agent [2]120, if the device is inactive for the amount of time specified in thePIN lock policy, the device will automatically lock.

A second merging rule is an integer merging rule. According to theinteger merging rule, if the policies are enumerated from least secureto most secure, or vice versa, the policy with the most secure settingwill trump the other policies. An example of this rule is a passwordlength policy. For example, if a policy issued from management agent [1]110 requires a password length of four and a policy issued frommanagement agent [2] 120 requires a password length of five, the policyrequiring the longer password would trump the policy that requires fewernumbers. Therefore, the policy requiring a password length of 5 would bethe policy that is enforced. In contrast, in data specific policies, thesmallest number may be determined to be the most secure policy. Forexample, management agent [1] 110 may issue a policy that limits thenumber of email messages stored on the device to a specific number(e.g., 25). Management agent [2] 120 may issue a policy that permitsthirty email messages to be stored on the mobile device 150. Inembodiments, the policy that allows the smallest number of messages tobe stored on the device, namely the policy issued from management agent[1] 110, is determined to be the most secure policy.

A third rule for policy merging is the allow sets rule. According tothis rule, the policies set forth by the management agents enumerate alist of actions, programs, or procedures that are allowed to be executedon the mobile device 150. When policies are merged using this rule, theglobal policy will consist of the intersection of the various individualpolicies. For example, if management agent [1] 110 allows programs A, B,and C to run while management agent [2] 120 allows programs B, C, and Dto be run, the resulting intersecting set would allow only programs Band C to be run on the mobile device 150.

A fourth rule of policy merging is the restriction sets rule. Accordingto this rule, the policies set forth by the management agents enumeratea list of actions, programs or procedures that are not allowed to beexecuted on the device. When the policies are merged, the resultingglobal policy will consist of the union of the various individualpolicies. Therefore, if management agent [1] 110 does not allowexecution of programs A and B and management agent [2] does not allowexecution of programs B and C, the global policy will not allowexecution of programs A, B and C on the mobile device 150.

Once the policies have been merged according to one or more rules listedabove, step 240 provides that the global policy is applied to thedevice. As indicated above, the policies may be device wide policies,such as PIN lock, camera controls, etc. while other policies may be dataspecific policies. According to embodiments, the device wide policiesmay be merged and the resulting global policy applied to the device whenconnecting to each one of the plurality of management agents. Forexample, when the mobile device 150 connects to any of the managementagents, the most secure policy from each category issued by managementagent [1] 110, management agent [2] 120, and management agent [n] 130 isapplied to the mobile device 150.

However, data specific policies need not always be merged. In someembodiments, the data specific policies are merged and the resultingglobal policy applied to all accounts. Alternatively, in otherembodiments, the merge rules are not applied to the various dataspecific policies and each data specific data policy is enforced onlywhen the mobile device 150 connects to the management agent that issuedthe specific data policy.

In embodiments, the global policy may contain a combination of devicewide policies and data specific policies. While the device wide policiesare applied on the device regardless of which management agent themobile device 150 is currently connected to, a subset of data specificpolicies may be enforced only when the mobile device is connected to themanagement agent that issued the subset of the data specific policies.In other embodiments, data specific policies may be applied continuouslyto any data stored on the device, regardless of whether the data thatwas retrieved from the network (e.g., servers, computers or otherstorage devices) associated with the given management agent.

FIG. 3 is an operational 300 flow for performing updates to themanagement policies of the mobile device according to embodiments. Flow300 may be implemented when a relationship between a management agentand the mobile device is severed, when a new relationship between themobile device 150 and a new management agent begins, when a relationshipbetween the mobile device 150 and a management agent is renewed, or whenone of the management agents updates, adds or deletes a policy in itspolicy container.

In step 310, an updated policy is received by the mobile device 150. Theupdated policy may result from an added policy, an updated policy or theexclusion of a policy (e.g., adding or removing a PIN lock policy orchanging a password length policy). In other embodiments, the flow 300may be trigged by one management agent severing a relationship with themobile device 150. In yet other embodiments, the flow 300 may be triggedby the mobile device 150 severing a relationship with the managementagent. When a relationship between a management agent and the mobiledevice 150 is severed, each policy provided by that particularmanagement device is no longer applied by the mobile device 150.

Once it is determined that a policy has been updated or removed, step320 provides that the most secure policy, for each category isrecalculated. Thus, continuing with the example from above, managementagent [1] 110 may change its password length policy to have a minimumlength of six characters. Once the update is received, the mobile device150 will compare the updated policy with all other policies in the samecategory to determine which policy is now the most secure. Because apolicy requiring a six character password is more secure than a policyrequiring a five character password, the policy requiring 6 charactersis merged with the remaining most secure policies from the remainingcategories.

According to an embodiment, the mobile device 150 may store data thatidentifies which management agent issued each of the policies. Thisprovides a means whereby users can determine which policies are beingenforced by each of the management agents. Thus, a user of the mobiledevice knows which policies will no longer be enforced when therelationship with a particular management agent is severed. This alsoallows the mobile device to more quickly determine what policies need tobe rolled back, recalculated and merged to create a new global policywhen a policy has been updated, added or removed.

In embodiments, when a relationship between the mobile device 150 andone of the management agents has been severed, the policies that wereissued by the remaining management agents are compared and a newdetermination is made as to which policies are the most secure. Aspreviously explained, the mobile device 150 may store data thatindicates what policies are issued from each of the management agents.It can also be determined whether any of the policies issued by themanagement agent were classified as the most secure policy in any of thecategories. In instances where none of the policies were determined tobe the most secure, there is no need to recalculate the most securepolicies in each category as they remain unchanged. However, inembodiments, it may be desirable to recalculate the security rating ofeach of the remaining policies. This ensures that the aggregate list ofapplicable policies is always up to date.

Once the most secure policy for each category have been recalculated,step 330 provides that the new set of most secure policies are mergedtogether to create a new global policy. According to embodiments thepolicies are merged according to one or more of the merge rules (binary,integer, allow sets, and restriction sets) indicated above.

When the new global policy has been created, step 340 provides that thenew global policy is applied to the mobile device 150. According toembodiments, the new global policy may contain both device wide policiesand/or data specific policies. In embodiments, the device wide policiesmay be applied globally while the data specific may or may not requiremerging. In alternative embodiments the global policy may contain acombination of device wide and data specific policies. In otherembodiments some of the data specific policies may require merging,while other data specific policies are only enforced when the mobiledevice connects to the management agent that issued the data specificpolicy. In yet other embodiments, data specific policies may not requirea connection to the specific agent that issued them and the dataspecific policies may be applied continuously to any data stored on themobile device 150 that was retrieved from the network (servers,computers or other storage devices) associated with the given managementagent.

FIG. 4A illustrates how policies from a plurality of disparatemanagement agents are merged according to embodiments. The policiescontained in each policy container 400, 410, and 420 may be merged usingthe one or more of the merging rules described above. Although thepolicies in FIG. 4A, as well as the policies illustrated in FIGS. 4B-4Care specific policies, it is to be understood that the policies listedin each of the policy containers are for illustrative purposes and arenot limiting.

As illustrated in FIG. 4A, policy container [1] 400 may contain twopolicies: a PIN lock policy 402 and a password length policy 404. Policycontainer [2] 410 may contain 3 policies: a PIN lock policy 412, apassword length policy 414, and a policy that restricts emailattachments 416 from being received on the mobile device 150. Policycontainer [n] 420 may include two policies: an encrypted email policy422 and a disable Bluetooth policy 424. Each policy container [1], [2],and [n] 400, 410, and 420 may be a policy container issued frommanagement agent [1] 110, management agent [2] 120 and management agent[n] 130 respectively.

When the mobile device 150 receives each policy container and thecorresponding policies, a determination is made as to which policy ineach policy category is the most secure. For example, because policycontainer [1] 400 and policy container [2] 410 each have a PIN lockpolicy 402 and 412, and a password length policy 404 and 414, adetermination is made as to which policies are the most secure withrespect to these two categories.

In an embodiment, the PIN lock policy contained in policy container [1]400 may require that the device be locked after 5 minutes of inactivity.The PIN lock policy contained in policy container [2] 410 may requirethat the device be locked after the device has been inactive for 10minutes. Because automatically locking the device after 5 minutes ofinactivity is more secure, the PIN lock policy 402 is included in theglobal policy container 430. In instances where neither policy isdetermined to be the most secure (e.g., both PIN lock policies have amaximum time of inactivity of 5 minutes) the policy that issued from themanagement agent with the first in time relationship may be the policythat is applied.

Continuing the example, the password length policy 404 may require apassword of 4 characters while password length policy 414 may require apassword of 6 characters. Using the integer rule explained above,password length policy 414 is determined to be the most secure policy.When the policies are subsequently merged, policy 414 will be includedin the global policy container 430.

Policy container [2] 410 may also include a policy that restricts emailattachments from being received on the device according to embodiments.Because none of the other policy containers have a similar policy, thebinary rule determines that restricting email attachments is more securethan allowing email attachments. As a result, the no email attachmentspolicy 416 is included in the global policy container 430. It should benoted that the no email attachments policy 416 may be a data specificpolicy and therefore, may be applied by the mobile device 150 regardlessof which management agent the mobile device is connecting to.Alternatively, the policy may only applied when the device is connectingto the management agent, or servers and data sources associated with themanagement agent that issued the policy.

Still continuing with the example, policy container [n] 420 may includean encrypted email policy 422 and a disable Bluetooth policy 424. Usingthe merging rules above, and determining that policies 422 and 424 arethe only policies in their respective categories, policies 422 and 424are determined to be the most secure. When the policies are subsequentlymerged, policies 422 and 424 will be included in the global policycontainer 430.

As with the no email attachments policy 416, the encrypted email policy422 may be a data specific policy. Therefore, the encrypted email policy422 may be merged and applied globally to all management agents. Inother embodiments, the encrypted email policy 422 is only applied whenthe mobile device 150 connects to the management agent that issued thepolicy or when the mobile device 150 connects to servers or other datasources that are associated with the management agent.

As a result of running the various merging rules, the global policycontainer 430 contains the most secure policy from each category.

FIG. 4B illustrates merging updated policies from a plurality ofdisparate management agents when a policy has been removed from a policycontainer. In this example, policy container [1] 400 and policycontainer [2] 410 have the same policies above with respect to FIG. 4A.However, management agent [n] 120 has removed the encrypted email policy422 from the policy container [n] 420. As a result, the policies arerolled back, a new set of the most secure policies are determined, andthe policies are merged based on the merge rules. Because the encryptedemail policy 422 no longer exists, this particular policy is removedfrom the global policy container 430. Thus, email messages sent to andfrom the device 150 may no longer need to be encrypted.

Continuing with the example, management agent 100 may have updated thepassword length policy 404. The updated password length policy 404 maynow require seven characters instead of four. As a result, the passwordlength policy 404 is now the most secure policy. The password lengthpolicy 404 is then merged with the other remaining most secure policies(e.g., PIN lock 404, No Email attachments 416, and disable Bluetooth424). According to embodiments, it may not be necessary to recalculateeach of the most secure policies for each category. When a policy for aparticular category is updated, the device may compare the updatedpolicy value with the current most secure policy of that particularcategory. Based on the comparison, a determination is made as to whetherthe updated policy trumps the current most secure policy of thecategory. If the updated policy does not trump the current most securepolicy, the global policy remains unchanged. If however, the updatedpolicy trumps the current secure policy of the category, an update mustbe performed.

FIG. 4C illustrates merging policies from a plurality of disparatemanagement agents when a relationship between the mobile device and amanagement agent has been severed. Continuing with the example from FIG.4B, the relationship between management agent [2] 110 and the mobiledevice 150 has now been terminated. As a result, policy container [2]410 along with its corresponding policies are no longer applied to themobile device 150.

When the policies from the removed management agent are no longer beingenforced on the mobile device 150, the remaining policies from eachremaining policy container are rolled back and a new calculation isperformed to determine which of the remaining policies, in each of theremaining categories, are the most secure. Continuing the example fromabove, because each of the remaining policies are in separatecategories, applying the merging rules yields a global policy container430 having the PIN lock policy 402, the password length policy 404 andthe disable Bluetooth policy 424. Each of the remaining policies aredevice wide policies, and therefore, the policies are applied to themobile device 150 regardless of whether the device is connecting tomanagement agent [1] 100 or management agent [n] 130.

FIG. 5 illustrates a merging rule for merging policies from a pluralityof disparate management agents.

According to embodiments, the allow sets rule as explained above, allowsactions, programs or procedures to be executed on the device so long aseach management agent allows the action to be executed. For example,management agent [1] 110 may issue a policy container [1] 500 havingpolicies which enable Bluetooth 502 and enable camera operations 504.Management agent [2] 120 may issue policy container [2] 510 whichincludes policies for enabling Bluetooth 512, enabling camera operations514, and enabling web-based email programs 516. Management agent [n] 130may issue policy container [n] having policies that enable Bluetooth 522and enable web-based email 524. Applying the allow sets merge rule, theintersection of each individual policy is taken and the resulting globalpolicy container 530 has a single policy—the enable Bluetooth policy502. As a result, when the global policy 530 is applied to the mobiledevice 150, Bluetooth capabilities of the device will be enabled whileother device functionalities (e.g., camera operations) are disabled.

FIG. 6 illustrates another merging rule for merging policies from aplurality of disparate management agents.

According to embodiments, the restriction sets merging rule enumerates alist of actions, programs or procedures that are not allowed to beexecuted by the mobile device 150. When merging these types of policies,the resulting global policy container 630 includes an aggregate list ofthe union of the various individual policies. For example, managementagent [1] 110 may issue policy container [1] 600 which includes adisable Bluetooth policy 602 and a disable camera operations policy 604.Management agent [2] 120 may issue policy container [2] 610 having adisable flash card reader policy 612. Management agent [n] 130 may issuepolicy container [n] 620 having a disable web-based email policy 622.

Performing a union on these policies yields a global policy container630 that includes each of the policies listed above (e.g., policies 602,604, 612 and 622). As a result, when the global policy 630 is applied tothe mobile device 150, the device may not use the Bluetoothcapabilities, the camera, or the flash card reader. According toembodiments, the disable web-based email policy 622 may be a dataspecific policy and depending on the implementation, may be appliedglobally or may only be applied when the device connects to managementagent [n] 130. In other embodiments, the data specific policy may beapplied to servers or data sources associated with management agent [n]130.

With reference to FIG. 7, an embodiment of a computing environment forimplementing the various embodiments described herein includes acomputer system, such as computer system 700. Any and all components ofthe described embodiments may execute as or on a client computer system,a server computer system, a combination of client and server computersystems, a handheld device, and other possible computing environments orsystems described herein. As such, a basic computer system applicable toall these environments is described hereinafter.

In its most basic configuration, computer system 700 comprises at leastone processing unit or processor 704 and system memory 706. The mostbasic configuration of the computer system 700 is illustrated in FIG. 7by dashed line 702. In some embodiments, one or more components of thedescribed system are loaded into system memory 706 and executed by theprocessing unit 704 from system memory 706. Depending on the exactconfiguration and type of computer system 700, system memory 706 may bevolatile (such as RAM), non-volatile (such as ROM, flash memory, etc.),or some combination of the two.

Additionally, computer system 700 may also have additionalfeatures/functionality. For example, computer system 700 includesadditional storage media 708, such as removable and/or non-removablestorage, including, but not limited to, magnetic or optical disks ortape. In some embodiments, software or executable code and any data usedfor the described system is permanently stored in storage media 708.Storage media 708 includes volatile and non-volatile, removable andnon-removable media implemented in any method or technology for storageof information such as computer readable instructions, data structures,program modules, or other data.

System memory 706 and storage media 708 are examples of computer storagemedia. Computer storage media includes RAM, ROM, EEPROM, flash memory orother memory technology, CD-ROM, digital versatile disks (“DVD”) orother optical storage, magnetic cassettes, magnetic tape, magnetic diskstorage, other magnetic storage devices, or any other medium which isused to store the desired information and which is accessed by computersystem 700 and processor 704. Any such computer storage media may bepart of computer system 700. In embodiments, system memory 706 and/orstorage media 708 stores data used to perform the methods or form thesystem(s) disclosed herein. In embodiments, system memory 706 storesinformation such as policy data 714 which indicates among other things,which management agent issued each policy and which policy in eachcategory is the most secure policy. In embodiments system memory 706also stores the merging rules 716.

Computer system 700 may also contain communications connection(s) 710that allow the device to communicate with other devices. In embodiments,communications connection(s) 710 may be used to transmit and receivemessages between sender devices, intermediary devices, and recipientdevices. Communication connection(s) 710 is an example of communicationmedia. Communication media may embody a modulated data signal, such as acarrier wave or other transport mechanism and includes any informationdelivery media, which may embody computer readable instructions, datastructures, program modules, or other data in a modulated data signal.The term “modulated data signal” means a signal that has one or more ofits characteristics set or changed in such a manner as to encodeinformation or a message in the data signal. By way of example, and notlimitation, communication media includes wired media such as a wirednetwork or direct-wired connection, and wireless media such as anacoustic, RF, infrared, and other wireless media. In an embodiment, themethods described above may be transmitted over the communicationconnection(s) 710.

In some embodiments, computer system 700 also includes input and outputconnections 712, and interfaces and peripheral devices, such as agraphical user interface. Input device(s) are also referred to as userinterface selection devices and include, but are not limited to, akeyboard, a mouse, a pen, a voice input device, a touch input device,etc. Output device(s) are also referred to as displays and include, butare not limited to, cathode ray tube displays, plasma screen displays,liquid crystal screen displays, speakers, printers, etc. These devices,either individually or in combination, connected to input and outputconnections 712 are used to display the information as described herein.All these devices are well known in the art and need not be discussed atlength here.

In some embodiments, the component described herein comprise suchmodules or instructions executable by computer system 700 that may bestored on computer storage medium and other tangible mediums andtransmitted in communication media. Computer storage media includesvolatile and non-volatile, removable and non-removable media implementedin any method or technology for storage of information such as computerreadable instructions, data structures, program modules, or other data.Combinations of any of the above should also be included within thescope of readable media. In some embodiments, computer system 700 ispart of a network that stores data in remote storage media for use bythe computer system 700.

This disclosure described some embodiments of the present disclosurewith reference to the accompanying drawings, in which only some of thepossible embodiments were shown. Other aspects may, however, be embodiedin many different forms and should not be construed as limited to theembodiments or examples set forth herein. Rather, these embodiments andexamples were provided so that this disclosure was thorough and completeand fully conveyed the scope of the possible embodiments to thoseskilled in the art.

Although the embodiments have been described in language specific tostructural features, methodological acts, and computer-readable mediacontaining such acts, it is to be understood that the possibleembodiments, as defined in the appended claims, are not necessarilylimited to the specific structure, acts, or media described. One skilledin the art will recognize other embodiments or improvements that arewithin the scope and spirit of the present disclosure. Therefore, thespecific structure, acts, or media are disclosed only as illustrativeembodiments. The disclosure is defined by the appended claims.

What is claimed is:
 1. A system, comprising: at least one processor; anda memory storing instructions, which, when executed by the at least oneprocessor, perform a method for managing policy settings of a mobiledevice, comprising: receiving a first policy container from a firstmanagement agent, wherein the first policy container comprises a firstpolicy corresponding to a policy category; receiving a second policycontainer from a second management agent, wherein the second policycontainer comprises a second policy, wherein the second policycorresponds to the policy category; merging the first policy containerand the second policy container to generate a global management policycomprising a most secure policy for the policy category determined basedon a comparison of the first policy and the second policy; storingpolicy data, wherein the policy data comprises an indication of anassociation between an issuing management agent and the most securepolicy, wherein the issuing management agent is one of the firstmanagement agent and the second management agent; receiving anindication of a modified relationship with at least one of the firstmanagement agent and the second management agent; generating an updatedglobal management policy based on the stored association between theissuing management and the most secure policy; and applying the sameupdated global management policy to the mobile device when the mobiledevice connects to the first management agent and when the mobile deviceconnects to the second management agent.
 2. The system of claim 1,wherein the comparison of the first policy and the second policycomprises: generating security ratings for the first policy and thesecond policy; and comparing the security ratings for the first policyand the second policy.
 3. The system of claim 1, wherein the modifiedrelationship is one or more selected from a group consisting of:severing a relationship; initiating a new relationship; renewing arelationship; and updating of a management agent.
 4. The system of claim1, wherein generating the updated global management policy comprises:determining that a relationship between the issuing management agent andthe mobile device is severed; performing an evaluation of the storedassociation between the issuing management agent and the most securepolicy; determining a new most secure policy based on the evaluation;and generating the updated global management policy comprising the newmost secure policy.
 5. The system of claim 1, wherein the indication ofthe modified relationship indicates a new relationship with a thirdmanagement agent.
 6. The system of claim 5, wherein generating theupdated global management policy comprises: receiving a third policycontainer from the third management agent, wherein the third policycontainer comprises a third policy corresponding to the policy category;determining the third policy is more secure than the most secure policy;generating the updated global management policy comprising the thirdpolicy as a new most secure policy; and updating stored policy data tocomprise an association between the third management agent and the newmost secure policy.
 7. The system of claim 6, wherein updated storedpolicy data further comprises removing the association between theissuing management agent and the most secure policy.
 8. A method formanaging policy settings of a mobile device, comprising: receiving afirst policy container from a first management agent, wherein the firstpolicy container comprises a first policy corresponding to a policycategory; receiving a second policy container from a second managementagent, wherein the second policy container comprises a second policy,wherein the second policy corresponds to the policy category; mergingthe first policy container and the second policy container to generate aglobal management policy comprising a most secure policy for the policycategory determined based on a comparison of the first policy and thesecond policy; applying the global management policy to the mobiledevice, wherein the global management policy is applied to the mobiledevice when the mobile device is connected to the first management agentand the global management policy is applied to the mobile device whenthe mobile device is connected to the second management agent;generating a global policy display comprising one or more policiesapplied to the mobile device and an associated management agent for eachof the one or more policies, wherein the global policy display indicatesthe most secure policy is associated with the issuing management agent;and presenting the generated global policy display on the mobile device.9. The method of claim 8, further comprising: storing policy data,wherein the policy data comprises an indication of an associationbetween an issuing management agent and the most secure policy, whereinthe issuing management agent is one of the first management agent andthe second management agent.
 10. The method of claim 9, wherein theglobal policy display is generated based at least in part on the storedpolicy data.
 11. The method of claim 8, wherein the comparison of thefirst policy and the second policy comprises: generating securityratings for the first policy and the second policy; and comparing thesecurity ratings for the first policy and the second policy.
 12. Themethod of claim 8, further comprising: receiving an indication of amodified relationship with at least one of the first management agentand the second management agent; and updating the generated globalpolicy display as a result of the received indication.
 13. The method ofclaim 8, further comprising: receiving a third policy container from athird management agent, wherein the third policy container comprises athird policy corresponding to the policy category; determining the thirdpolicy is more secure than the most secure policy; generating theupdated global management policy comprising the third policy as a newmost secure policy; and updating the global policy display to indicatethe new most secure policy, wherein the updated global policy displaycomprises an indication that the new most secure policy is associatedwith the third management agent.
 14. A method for managing policysettings of a mobile device, comprising: receiving a first policycontainer from a first management agent, wherein the first policycontainer comprises a first policy corresponding to a policy category;receiving a second policy container from a second management agent,wherein the second policy container comprises a second policy, whereinthe second policy corresponds to the policy category; merging the firstpolicy container and the second policy container to generate a globalmanagement policy comprising a most secure policy for the policycategory determined based on a comparison of the first policy and thesecond policy; storing policy data, wherein the policy data comprises anindication of an association between an issuing management agent and themost secure policy, wherein the issuing management agent is one of thefirst management agent and the second management agent; receiving anindication of a modified relationship with at least one of the firstmanagement agent and the second management agent; generating an updatedglobal management policy based on the stored association between theissuing management and the most secure policy; and applying the sameupdated global management policy to the mobile device when the mobiledevice connects to the first management agent and when the mobile deviceconnects to the second management agent.
 15. The system of claim 14,wherein the comparison of the first policy and the second policycomprises: generating security ratings for the first policy and thesecond policy; and comparing the security ratings for the first policyand the second policy.
 16. The system of claim 14, wherein the modifiedrelationship is one or more selected from a group consisting of:severing a relationship; initiating a new relationship; renewing arelationship; and updating of a management agent.
 17. The system ofclaim 14, wherein generating the updated global management policycomprises: determining that a relationship between the issuingmanagement agent and the mobile device is severed; performing anevaluation of the stored association between the issuing managementagent and the most secure policy; determining a new most secure policybased on the evaluation; and generating the updated global managementpolicy comprising the new most secure policy.
 18. The system of claim14, wherein the indication of the modified relationship indicates a newrelationship with a third management agent.
 19. The system of claim 18,wherein generating the updated global management policy comprises:receiving a third policy container from the third management agent,wherein the third policy container comprises a third policycorresponding to the policy category; determining the third policy ismore secure than the most secure policy; generating the updated globalmanagement policy comprising the third policy as a new most securepolicy; and updating stored policy data to comprise an associationbetween the third management agent and the new most secure policy. 20.The system of claim 19, wherein updated stored policy data furthercomprises removing the association between the issuing management agentand the most secure policy.